An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Apple’s review process this time has been incredibly frustrating. My app waited almost a month before it was finally reviewed, and then it was rejected under: Guideline 2.3.1(a) - Hidden Features Apple claimed that the app contains hidden features. Guideline 4.2 - Minimum Functionality Apple claimed that the app provides limited functionality and feels too similar to a web browsing experience. But that does not match my app at all. It is a native social alarm clock app with features including: Alarm scheduling with AlarmKit Real-time voice rooms Live Activities Widgets Siri Shortcuts / App Intents QR code invitation scanning Apple Music custom ringtones Push notifications This is clearly not just a wrapped website. The only WebView usage is for standard settings pages such as Privacy Policy, Terms of Service, and FAQ. What makes it even more frustrating is that now, whether I wait for Apple’s reply or resubmit the app, I have no idea how long it will take. In the past, Apple Developer Support at least offered phone support for real-time help. Recently, I’ve only been seeing email as the contact option, and after waiting a long time, the reply often feels like a generic AI-written template that does not actually help. It really makes Apple feel increasingly dismissive of developers. Even an app with in-app purchases, which also makes money for Apple, can get stuck in review for this long. Meanwhile, my coworker submitted an app without in-app purchases later than I did, and it was approved within a week. It is hard not to feel frustrated by how inconsistent and opaque the review process has become.

My subscriptions have a status of "developer action needed", but when I attempt to save an edit I receive an error "There was an error with editing your App Store localization. Try again later." Refreshing the page doesn't change anything. I have 2 localizations, one of them has a status of "waiting for review". I am unable to attach the subscription group to my binary as the ready to submit status required for the In-App Purchases and Subscription section to become active is not achievable. I have emailed and received no response. My app has been approved and is live on the app store with subscriptions that do not function. I understand I made an error, this is my first time releasing on the app store.

Hi, I have paid my Apple developer fees and what I understand is I will have my apps reviewed and feedback given in a reasonable amount of time. However, its been more than 2 weeks, 2 expedited review requests and 2 support requests that have been ignored. Is this a common experience. They said most apps get reviewed with 2-3 days. If they don't provide any feedback, how do we proceed? I have marketing pipeline ready to launch and I can't plan the timeline with this behaviour.

My app has been stuck in "Waiting for review" for longer than usual. I just wanted to check and see if there are delays or something else is going on that I can fix. Thank you.

Hi everyone, My app has been stuck on "In Review" for about 3 days now. Before that, it also spent around 3 days in "Waiting for Review," so the total time has been close to 6 days. From what I’ve seen in the past, it usually takes 2–3 days to move from "Waiting for Review" to "In Review," and then only a few hours to get a decision once the review actually starts. However, this time it seems different. Based on my server/Firebase logs, it doesn’t look like the reviewer has opened the app yet or created a test account, so it seems like the review may not have actually started. This is my first app submission, so I’m not sure if that might affect the timeline. Has anyone experienced something similar recently? Is this normal, or is there something I should do (for example, contacting App Review or requesting an expedited review)? Any advice would be appreciated.

My app has been stuck on "In Review" for about 3 days now. Before that, it also spent around 3 days in "Waiting for Review," so the total time has been close to 6 days. From what I’ve seen in the past, it usually takes 2–3 days to move from "Waiting for Review" to "In Review," and then only a few hours to get a decision once the review actually starts. However, this time it seems different. Based on my server/Firebase logs, it doesn’t look like the reviewer has opened the app yet or created a test account, so it seems like the review may not have actually started. This is my first app submission, so I’m not sure if that might affect the timeline. Has anyone experienced something similar recently? Is this normal, or is there something I should do (for example contacting App Review or requesting an expedited review)? Any advice would be appreciated.

Hello everyone, I am an iOS developer and my new app is having a long, unusual App Store review delay that I have not been able to resolve through the normal support channels. I have requested expedition, called every single day after a week of waiting and still no rejection, request additional information, or any sort of update. AppleID: 6759011581 Please help me resolve this issue, I have already had to push back multiple stakeholder meetings and deadlines.

Hello everyone, I would like to ask if other developers are currently experiencing long delays to approve an app. In my case, my macOS app update (version 1.1) has been stuck in “Ready for Review” for more than 8 days without entering the review phase. Timeline: • Feb 21 – Initial submission • Feb 22 – In Review • Feb 25 – Rejected • Feb 25 – Resubmitted • Mar 2 – In Review • Mar 2 – Rejected • Mar 5 (Wednesday) – Submitted again → Ready for Review • Today – Still Ready for Review, never entered In Review All issues mentioned in the previous rejections were fixed and the build was resubmitted successfully. What also confuses me is that in the App Review section I see a red exclamation mark, even though there are no unresolved messages and the build shows as submitted. I would like to ask: • Are others currently seeing unusually long delays? • Could this indicate a queue issue or system problem? • Has Apple changed something recently in the review pipeline? Normally my previous versions were reviewed and approved in a couple of days, so this delay seems quite unusual. Thanks in advance for any insight from other developers.

Hello App Review Team and iOS Developer Community, We submitted our iOS application on February 25, and within a few hours its status changed to “In Review.” Shortly after that, we received a call from the App Review team requesting some clarification. We provided the requested information during the call, and the same request was later posted in App Store Connect as an unresolved issue. We responded to the request within an hour, providing all the necessary details. However, since then we have not received any further updates regarding the review status. Because this application is related to upcoming sports events, the timing is quite critical. Our client, who owns the sports rights, had planned a launch event on March 6, but unfortunately it had to be postponed because the iOS app was not yet available on the App Store. The sports events are scheduled to begin next week, and our client is planning a marketing campaign ahead of the events, which depends on the app being available. We have already: Submitted an Expedited Review request Contacted Apple Support twice via email At the moment we are unsure how to proceed, as we expected the review process to be completed within the typical 24 hour timeframe mentioned in Apple’s documentation. Does anyone know if there is any additional way to contact the App Review team or any steps we can take to help move the review forward? If any Apple staff member is able to look into this, we would be happy to provide the App ID or additional details via a private support channel if needed. Thank you for your support.

I have a urgent needs to fix a breaking change to the App, and it has no status update or response.

The contact us page on apple developer is showing error and henceforth not able to contact the apple team also https://developer.apple.com/contact/app-store/?topic=expedite is not working showing no apps available which blocks us reaching to apple team for resolution. we are just waiting for an update to launch our new apps

Hello everyone, My app has been in "Waiting for Review" status since February 20, and it still hasn’t moved to the review stage yet. On March 9, I submitted a support ticket asking whether there might be any issue with my submission or if additional information is required from my side. However, I have not received any response from Apple so far. At this point, I’m not sure if I should continue waiting or if there is anything else I should do to resolve the situation. App ID: 6759365919 Ticket ID: 102839874589 If anyone has experienced a similar situation or if an Apple staff member could help check the status, I would really appreciate it. Thank you very much.

I have app update that’s been waiting for review since 4th February. I’ve raised a case, posted to the case a few times, been told twice by support that I ‘haven’t been forgotten’ and yet nothing changes and no useful communication. It’s an update to an existing published app. I have other apps waiting for review and TestFlight approval for almost as long. Now approaching 10% of my year’s developer subscription has already been spent just waiting. What‘s the answer here? I am reticent to reject and resubmit As there’s no evidence that that would make any difference. None of the app updates I’ve submitted for other apps after this one have been reviewed either.

Hello, We are hoping someone from Apple or other developers who have encountered this recently can help clarify the correct process, as we appear to be stuck between the current App Store Connect UI and documentation that references an older submission flow. Issue during App Review Our app is being rejected with: Guideline 2.1(b) – Performance – App Completeness Subscriptions in the app were still unavailable for users to purchase. However, the subscriptions do exist and are configured correctly in App Store Connect. The app contains four auto-renewable subscriptions (monthly and yearly tiers across two service levels). All of them are currently in “Waiting for Review” status. The app uses RevenueCat with StoreKit to retrieve products. When products are still Waiting for Review, Apple does not return them to StoreKit, which results in the app correctly reporting that the subscriptions are unavailable. Because of this, it appears that the reviewer may be testing the app before the subscriptions have been approved, preventing StoreKit from returning the products. Problem with Apple documentation / submission workflow The responses we are receiving from App Review repeatedly point us to the documentation: “Submit an In-App Purchase” (App Store Connect Help → Manage submissions to App Review) This documentation states that subscriptions must be attached to the app version using the: “Select In-App Purchases or Subscriptions” option on the version page. However, this control does not exist in our App Store Connect interface. Our interface appears to follow the newer App Store Connect submission flow, where subscriptions are configured and submitted from their own product pages, and are automatically bundled with the app submission. Because of this: The “Select In-App Purchases or Subscriptions” step referenced in the documentation cannot be completed. There is no “Add” or “Select” button on the version page. This leaves us stuck in a loop where: Apple support points us to documentation describing the older workflow. The step described in the documentation does not exist in the current UI. The app is reviewed before the subscriptions are approved, causing the purchase flow to appear unavailable. Attempts to resolve We have already: Verified product identifiers match between App Store Connect and RevenueCat Confirmed RevenueCat is using the correct Apple public SDK key Verified the offerings and packages are correctly configured Confirmed the app fetches the correct product identifiers Followed the “Submit an In-App Purchase” documentation thoroughly Despite this, we cannot complete the step described in the documentation because the UI element referenced there is not present. Additionally, we have: Submitted multiple App Store Connect review responses Submitted multiple support requests Unfortunately, the replies we receive continue to reference the same documentation without addressing the specific issues described above. What we are hoping to clarify We would really appreciate if someone could address the following questions specifically, rather than pointing us back to the same documentation: In the current App Store Connect submission flow, how are subscriptions supposed to be associated with a new app version if the “Select In-App Purchases or Subscriptions” option no longer exists? When subscriptions are Waiting for Review, will StoreKit return them to the app during App Review, or must they be approved first before they can be fetched? Is there anything additional required in the new submission flow to ensure subscriptions are reviewed and available before the app is evaluated? Request If someone from Apple or another developer who has encountered this recently could please respond directly to the issues described above, it would be greatly appreciated. At the moment we appear to be stuck between: documentation referencing a previous App Store Connect workflow, and the current UI, which does not allow that documented step to be completed. Thank you for your time, and any clarification would be very helpful.

Hello everyone, I am an iOS developer and both my apps are experiencing an unusual App Store review delay that I have not been able to resolve through the normal support channels. These are existing apps on app store with simple updates. It has not moved to “In Review”, and I have not received any rejection message or request for additional information from the App Review team. AppleID: 6756242440 and 6746870245 Please help us resolve the issue. Thanks in advance

Hello, I’m posting here to ask for guidance and to see if anyone has experienced a similar situation. More than 30 days ago, I submitted an appeal to the App Review Board after receiving a Pending Termination Notice for my Apple Developer Program account. However, I have not received any response or update since submitting the appeal. In the notice, Apple mentioned that my account was associated with “dishonest or fraudulent activity” related to app submissions. I want to clarify that I did not intentionally attempt to bypass the App Review process. The only change I made around that time was editing some app metadata (subtitle keywords) while trying to optimize my Apple Search Ads campaign. Looking back, I now understand that some of those keywords may have been interpreted as referencing content that Apple considers inappropriate for the App Store. After realizing this might have caused an issue, I immediately: Canceled the latest app submission that contained those metadata changes Explained the situation clearly in my appeal to the App Review Board Confirmed that I would avoid using similar metadata in the future Despite providing this explanation in my appeal, I have not received any reply or update for over a month, so I’m unsure about the current status of the appeal. If anyone here has gone through a similar process, could you share: How long it took to receive a response from the App Review Board? Whether it’s normal for appeals to take this long? Also, if any Apple staff happens to see this post, I would sincerely appreciate any guidance on whether my appeal is still under review or if there is anything further I should provide. Thank you very much for your time and help.

Dear Apple App Review Team, I am writing to formally escalate a situation that has become completely unacceptable. My application has been under review since February 4th at 20:21 — over one month ago — with no resolution and no meaningful communication from your team. I paid $99/year for an Apple Developer subscription specifically to publish and operate my application on the App Store. This is not a free service. I have paid for the right to distribute my app, and Apple is currently preventing me from doing so — for over 30 days — without any justification or timeline. This means I am paying for a service I am not receiving. That is, by any definition, a breach of the agreement between Apple and its developers. For reference, the application details are as follows: App Name: Daddy Tales App ID: 6758725133 I expect this matter to be treated with the urgency it deserves and to be taken care of immediately. I have already waited far too long. Sincerely

Hello everyone, Our application has been pending review since February 23rd. There's been no progress, and I'm not getting any concrete answers. My projects have suffered serious delays and inconvenience. What's going on at Apple? I've never waited this long before. Is there an explanation? Thank you for your help.

Hello App Review team and iOS developer community, I submitted an updated version of my app on App Store Connect on February 5, 2026, and it entered the review process on February 7, 2026. However, I do not understand why, as of today (March 8, 2026), its status is still "In Review." I have already contacted Developer Support on February 27, 2026 but have only received the following automated reply: “Thanks for submitting your support request. We’ve received your support request and will get back to you as soon as possible.” More than a month has passed, and I still haven’t received any official follow-up or updates from Apple regarding this issue My case ID : 102831527320 Apple ID : 1628986976 I would greatly appreciate your help in reviewing and approving this update as soon as possible, as the delay is affecting many users. Thank you for your support.

Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.